Limiting data transmission under lossy wireless conditions of an internet of things wireless device to facilitate a reduction of wireless retransmissions of the data

ABSTRACT

Limiting data transmission under lossy wireless conditions of an Internet of Things (IoT) wireless device to facilitate a reduction of wireless retransmissions of such data is presented herein. A method can comprise determining a characteristic of a radio frequency channel wirelessly coupling a wireless device to an access point device that has been configured to transfer data, which has been received from the wireless device, to a host device; and in response to the characteristic of the radio frequency channel being determined to satisfy a defined condition representing a degradation of a fidelity of the radio frequency channel, modifying, based on a determined classification of outbound data of the data that has been directed to the host device, a transmission of the outbound data to facilitate a reduction in wireless retransmissions of the outbound data due to the degradation of the fidelity of the radio frequency channel.

TECHNICAL FIELD

The subject disclosure generally relates to embodiments for limitingdata transmission under lossy wireless conditions of an Internet ofThings (IoT) wireless device to facilitate a reduction of wirelessretransmissions of the data.

BACKGROUND

Wireless connectivity of Internet of Things (IoT)/Machine-to-Machine(M2M) devices often correspond to lossy, error-prone radio/radiofrequency (RF) link conditions. In this regard, conventional wirelesstechnologies, e.g., cellular, satellite, etc. utilize transmissioncontrol protocol (TCP) based error mediation elements, e.g., errordetection, out-of-order packet detection, lost packet detection, forceduse of acknowledge (ACK)/negative acknowledgement (NAK) packets/signals,etc. to ensure data is received at a destination device with little/noerrors. However, retransmission of data by such TCP based errormediation elements incurs incremental monetary costs that are metered,billed, etc., e.g., via subscription based cellular, satellite, etc.services, according to an amount of data that has been transferred overa radio/RF link. Consequently, conventional wireless technologies havehad some drawbacks, some of which may be noted with reference to thevarious embodiments described herein below.

BRIEF DESCRIPTION OF THE DRAWINGS

Non-limiting embodiments of the subject disclosure are described withreference to the following figures, wherein like reference numeralsrefer to like parts throughout the various views unless otherwisespecified:

FIG. 1 illustrates a block diagram of an IoT wireless communicationenvironment comprising an RF fidelity layer of an IoT wireless deviceand an RF fidelity component of a host system, in accordance withvarious example embodiments;

FIG. 2 illustrates a block diagram of an end-to-end TCP stack of an IoTwireless communication environment, in accordance with various exampleembodiments;

FIG. 3 illustrates a block diagram of an IoT wireless device comprisingan RF fidelity layer, in accordance with various embodiments;

FIG. 4 illustrates a block diagram of another IoT wireless comprising anRF fidelity layer, in accordance with various embodiments;

FIG. 5 illustrates a block diagram of a host system comprising an RFfidelity component, in accordance with various embodiments;

FIG. 6 illustrates a block diagram of another host system comprising anRF fidelity component, in accordance with various embodiments;

FIG. 7 illustrates a block diagram of an IoT wireless device, inaccordance with various embodiments;

FIGS. 8-10 illustrate flowcharts of methods associated with an IoTwireless device comprising an RF fidelity layer, in accordance withvarious example embodiments;

FIGS. 11-14 illustrate flowcharts of methods associated with a hostsystem comprising an RF fidelity component, in accordance with variousembodiments;

FIG. 15 illustrates a block diagram of a wireless network environment,in accordance various example embodiments; and

FIG. 16 is a block diagram representing an illustrative non-limitingcomputing system or operating environment in which one or more aspectsof various embodiments described herein can be implemented.

DETAILED DESCRIPTION

Aspects of the subject disclosure will now be described more fullyhereinafter with reference to the accompanying drawings in which exampleembodiments are shown. In the following description, for purposes ofexplanation, numerous specific details are set forth in order to providea thorough understanding of the various embodiments. However, thesubject disclosure may be embodied in many different forms and shouldnot be construed as limited to the example embodiments set forth herein.

Conventional network technologies have had some drawbacks with respectto minimizing an impact of TCP-based retransmissions within a lossywireless environment. Various embodiments disclosed herein can improvecustomer experiences within an IoT ecosystem by monitoring wirelessconditions of IoT devices, sensors, etc. and controlling datatransmissions from/to such devices under lossy wireless conditions.

For example, a method can comprise determining, by a wireless devicecomprising a processor, e.g., an IoT device, sensor, etc. acharacteristic of an RF channel wirelessly coupling the wireless deviceto an access point (AP) device that has been configured to transferdata, which has been received from the wireless device, to a hostdevice, e.g., a home security system, a home automation system, abuilding monitor system, a building control system, etc. to facilitatefurther processing, evaluation, etc. of such data by application(s)executing on the host device.

In embodiment(s), the characteristic can comprise a received signalstrength indicator (RSSI), a bit error rate (BER), a reference signalreceived power (RSRP), a reference signal received quality (RSRQ), asignal-to-interference-plus-noise ratio (SINR), a block error rate(BLER), and/or a bit throughput corresponding to the RF channel. In thisregard, in an embodiment, an RF fidelity/functional layer of thewireless device, e.g., which has been communicating with an applicationexecuting on the wireless device and portion(s), layer(s), etc. of aprotocol stack, network protocol suite etc. of the wireless device, cansend control command(s), e.g., Attention (AT) command(s), to a radiomodule, e.g., a long term evolution (LTE) based radio module, of thewireless device to obtain the characteristic, e.g., viacommunication(s), register(s), memory location(s), etc. of the radiomodule.

In other embodiment(s), the RF fidelity/functional layer can obtain thecharacteristic via AT command(s) and/or probe(s), mechanism(s), etc. notexposed through the AT command(s). For instance, the characteristic,information, etc. associated with the RF channel, radio module, etc. canbe collected via other control command(s), method(s), etc., or viadirect monitoring of RF and/or data signals. Additionally, otherinformation collected by the RF fidelity/functional layer can compriseinformation about the wireless device, a corresponding system, e.g., APdevice, and/or a corresponding environment, e.g., comprising systemantenna capability (e.g., UE antenna capability, AP antenna capability,base station antenna capability, etc.); link loading; reduced power(e.g., reduced system power, reduced UE power, etc.); mobility speed;density of surrounding cell sites; UE battery state, etc.

In other embodiment(s), the RF fidelity/functional layer can probe,determine, monitor, etc. characteristic(s) of the RF channelcorresponding to a control channel between the wireless device and theAP device. In this regard, control messages/communications of thecontrol channel utilize wireless resources, device resources (e.g., theprotocol stack, network protocol suite, etc. of the wireless device),which are the same and/or similar to resources utilized to communicatedata message(s) via a data channel between the wireless device and theAP device. Accordingly, by monitoring characteristic(s) of the RFchannel via the control channel, the RF fidelity/functional layer canprobe, determine, monitor, etc. such characteristic(s) withoutartificially sending data packets, e.g., extra test packets, between thewireless device and the AP device using the data channel, e.g., withoutincurring extra data charges related to sending, via the data channel,the data packets, extra test packets, etc.

In yet other embodiment(s), the RF fidelity/functional layer can probe,determine, monitor, etc. characteristic(s) of the RF channel byobtaining information from the portion(s), layer(s), etc. of theprotocol stack, network protocol suite, etc. of the wireless device byobtaining information from devices, sensors, etc. of the wirelessdevice, etc. In this regard, such information can comprise: a determinedamount of media access control (MAC) retransmissions that have occurredwithin a defined period of time; an availability of access points near,in communication with, etc. the wireless device; a link loadingcorresponding to data packet transfers within the portion(s), layer(s),etc. of the protocol stack, network protocol suite, etc.; a transmissionpower of the wireless device; a mobility speed (e.g., rate of movement)of the wireless device, e.g., represented by a number of handoffs thathave been determined to have occurred within a defined period of time;an antenna capability (e.g., single, multiple-input multiple-output(MIMO), etc.) of the wireless device, an amount of RF interference,e.g., which has been determined to have occurred within a defined periodof time, etc.

In turn, in response to a determination that a monitored, probed, etc.characteristic of the RF channel satisfies a defined conditionrepresenting a degradation of a fidelity of the RF channel, the RFfidelity/functional layer can “tune”, modify, preempt, limit, reduce,withhold, delay, etc. a transmission of outbound data that has beendirected to the host device based on a determined classification (e.g.,critical/urgent/priority, non-critical/non-urgent/non-priority/normal,control, maintenance, update, standby, etc.) of the outbound data, e.g.,to facilitate a reduction in wireless, e.g., TCP-driven, retransmissionsof the outbound data due to the poor, lossy, error prone, degraded, etc.fidelity of the RF channel.

In this regard, in response to a determination that the fidelity of theRF channel is poor, lossy, error prone, degraded, etc., the RFfidelity/functional layer can maximize throughput of data/communicationsthat have been classified as critical/urgent/priority, and reduceconsumption of network device bandwidth corresponding to retransmissionof data/communications that have been classified asnon-critical/non-urgent/non-priority/normal, control, etc., e.g., byenabling, allowing, permitting, etc. transmission of thedata/communications that have been classified ascritical/urgent/priority, while limiting, reducing, withholding,delaying, etc. transmission of the data/communications that have beenclassified as non-critical/non-urgent/non-priority/normal, control, etc.

In an embodiment, in response to the determination that the fidelity ofthe RF channel is poor, lossy, error prone, degraded, etc., the RFfidelity/functional layer can limit, reduce, withhold, delay, etc. thetransmission of data/communications that have been classified asnon-critical/non-urgent/non-priority/normal, control, etc. untilcharacteristic(s) of the RF channel have been determined to improve. Inanother embodiment, the RF fidelity/functional layer can limit, reduce,withhold, delay, etc. the transmission of the data/communications thathave been classified as non-critical/non-urgent/non-priority/normal,control, etc. for a defined period of time, delay period, etc.

In one embodiment, the RF fidelity/functional layer can comprise amemory, buffers, first-in-first-out (FIFO) buffers, etc. to facilitatecollection of the data/communications that have been classified asnon-critical/non-urgent/non-priority/normal, control, etc., and laterfacilitate transmission of such stored, buffered, etc. data from thewireless device, e.g., based on a determination that the characteristicsof the RF channel have improved after the defined period of time, delayperiod, etc.

In another embodiment, in response to the determination that thefidelity of the RF channel is poor, lossy, error prone, degraded, etc.,the RF fidelity/functional layer can enable, allow, permit, etc.transmission of the data/communications that have been classified ascritical/urgent/priority, e.g., without limiting transmission of suchdata/communications.

In embodiment(s), an RF fidelity component of the host device can probe,determine, monitor, etc. characteristic(s) of the RF channel; and inresponse to the characteristic(s) of the RF channel being determined tosatisfy a defined condition representing a degradation of a fidelity ofthe RF channel, the RF fidelity component can modify, based on apriority level of outgoing data that has been directed to the wirelessdevice, a transmission of the outgoing data, e.g., to facilitate areduction of wireless retransmissions of the outgoing data due to thedegradation of the fidelity of the RF channel.

In an embodiment, the RF fidelity component can determine, predict, etc.a fidelity of the RF channel based on an analysis, evaluation, etc. ofinbound data that has been received from the wireless device. Forexample, the RF fidelity component can determine whether data,communications, etc. that have been received from the wireless devicesatisfy a defined condition representing the fidelity of the RF channelis poor, lossy, error prone, degraded, etc.

In this regard, in one embodiment, the RF fidelity component candetermine whether a majority of incoming communications that have beenreceived from the wireless device, e.g., over a defined period of time,have been classified as critical/urgent/priority, e.g., instead ofcomprising a mix of classifications, e.g., critical/urgent/priority,non-critical/non-urgent/non-priority/normal, control, etc.

In turn, in response to determining that a majority of the incomingcommunications have been classified as critical/urgent/priority, e.g.,without comprising the mix of classifications, the RF fidelity componentcan infer, determine, etc. that the fidelity of the RF channel is poor,lossy, error prone, degraded, etc. Further, based on the determinationthat the fidelity of the RF channel is poor, lossy, error prone,degraded, etc., the RF fidelity component can filter, limit, etc. atransmission of data from the host device to the wireless device, e.g.,enabling transmission of critical/urgent/priority data to the wirelessdevice, while preventing, withholding, etc. transmission of dataclassified as non-critical/non-urgent/non-priority/normal, control, etc.

For example, in one embodiment, in response to a classification of anincoming communication being determined to satisfy a defined conditionwith respect to an amount of critical/urgent/priority communicationsthat have been received during a defined period, e.g., representing thata majority of incoming communications that have been received over thedefined period have been classified as critical/urgent/priority, the RFfidelity component can withhold, delay, etc. a transmission of anon-critical/non-urgent/non-priority/normal, control, etc. communicationfrom the host device to the wireless device.

In turn, in another embodiment, in response to the characteristic of theRF channel being determined to satisfy a defined condition representingan improvement of the fidelity of the RF channel, e.g., representingthat a majority of incoming communications that have been received overthe defined period have been classified asnon-critical/non-urgent/non-priority/normal, control, etc., the RFfidelity component can send, transmit, etc. (e.g., without limiting,withholding, delaying, etc.) the transmission of thenon-critical/non-urgent/non-priority/normal, control, etc. communicationfrom the host device to the wireless device.

In yet another embodiment, in response to the classification of theincoming communication being determined to satisfy the defined conditionwith respect to the amount of priority communications that have beenreceived during the defined period, e.g., representing that the majorityof the incoming communications that have been received over the definedperiod have been classified as critical/urgent/priority, the RF fidelitycomponent can send, transmit, etc. (e.g., without limiting, withholding,delaying, etc.) a critical/urgent/priority communication directed towireless device.

In an embodiment, the RF fidelity component of the host device candetermine the fidelity of the RF channel based on information that hasbeen appended to data/communications that have been received, via thedata channel, from the wireless device. In this regard, in response todetermining that characteristic(s) of the RF channel satisfy a definedcondition representing that the fidelity of the RF channel is poor,lossy, error prone, degraded, etc., the RF fidelity layer of thewireless device can append information representing that the fidelity ofthe RF channel has been determined to be poor, error prone, degraded,etc. to existing data/communications readied to be sent to the hostdevice. In embodiment(s), the appended information can represent anRSSI, BER, RSRP, RSRQ, SINR, BLER, bit throughput, etc. corresponding tothe RF channel.

In turn, upon receipt of the data/communications comprising the appendedinformation, the RF fidelity component of the host device can remove,strip, etc. the appended information from the data/communications toobtain application data, and forward the application data to a hostapplication that is executing on the host device to facilitate furtherprocessing of the application data.

Further, in response to a determination, based on the appendedinformation, that the fidelity of the RF channel is poor, lossy, errorprone, degraded, etc., the RF fidelity component can filter, limit, etc.transmission(s) of communication(s)/data from the host device to thewireless device based on a determined classification of suchcommunications(s)/data, e.g., enabling transmissions ofcritical/urgent/priority data to the wireless device, while preventing,withholding, etc. transmissions of data classified asnon-critical/non-urgent/non-priority/normal, control, etc.

In another embodiment, in response to a determination, based on theappended information, that the fidelity of the RF channel is poor,lossy, error prone, degraded, etc., the RF fidelity component can send,transmit, etc. (e.g., without limiting, withholding, delaying, etc.)communication(s)/data that have been classified ascritical/urgent/priority directed to the wireless device.

In one embodiment, a machine-readable storage medium can compriseexecutable instructions that, when executed by a processor of a wirelessdevice, e.g., an IoT wireless device, facilitate performance ofoperations, comprising: creating an RF fidelity layer within an upperportion of a protocol stack of the IoT wireless device; monitoring, viathe RF fidelity layer, a characteristic of an RF link between the IoTwireless device and an AP device; and in response to the characteristicof the RF link being determined to satisfy a defined conditionrepresenting that a fidelity of the RF link is lossy, preempting, viathe RF fidelity layer, a transmission of data from the IoT wirelessdevice to a host device to facilitate a reduction in TCP-basedretransmissions of the data occurring under a lossy condition of the RFlink.

In an embodiment, the monitoring can comprise monitoring thecharacteristic of the RF link corresponding to a control channel betweenthe IoT wireless device and the access point device. In anotherembodiment, the preempting can comprise delaying a transmission of anon-urgent communication that has been directed to the host device.

Reference throughout this specification to “one embodiment,” “anembodiment,” etc. means that a particular feature, structure, orcharacteristic described in connection with the embodiment is includedin at least one embodiment. Thus, the appearances of the phrase “in oneembodiment,” “in an embodiment,” etc. in various places throughout thisspecification are not necessarily all referring to the same embodiment.Furthermore, the particular features, structures, or characteristics maybe combined in any suitable manner in one or more embodiments.

As mentioned above, conventional network technologies have had somedrawbacks with respect to minimizing an impact of TCP-basedretransmissions within lossy wireless environments. In this regard, TCPcan “mask” a lossy link layer via repeated retransmissions to correctfor lost/erred information packets, e.g., application developers programfunctions of a TCP device, e.g., a network edge device, assuming thatend-to-end connectivity may incur data flow backups/bottlenecks, whileremaining error free, e.g., utilizing wired connections. In turn,higher-level applications interfacing with lower TCP software/devicelayers, e.g., a TCP stack, “fire and forget” information to betransmitted, while the TCP stack is tasked with successfully deliveringthe information to its destination. In this regard, a network edgedevice in a lossy radio link can incur significant data overage chargesto transmit a given amount of information due to the increased billableretransmissions required to correct for link errors.

Further, while the TCP standard has limited semaphore/flag functionalitywithin the TCP stack, such functionality does not address the lossynessof a radio link. Further, although conventional network technologies maytry to address the lossyness of a radio link by creating applicationspecific codes, and sending such codes, via a network/radio edge device,to an application of a destination device to facilitate adjustment oftraffic flow, such use of application specific codes is fundamentallyflawed for at least the following reasons: 1) the application specificcodes must be sent over a radio link using a billable data channel on afrequent basis—as radio link fidelity may change over time—which canresult in even more billable data use over the radio link; and 2) theapplication specific codes are passed through the same lossy radio linkand are subject to the same failures/retries as the data payload that issubject to such failures/retries.

To address these and other concerns of conventional networktechnologies, various embodiments disclosed herein can improve customerexperiences within an IoT ecosystem by monitoring wireless conditions ofIoT devices, sensors, etc., and controlling data transmissions betweensuch devices and host system(s) based on determined classification(s) ofdata that have been transmitted between the devices and respective hostsystem(s)—without incurring additional data transfer charges, withoutincurring additional loading of an already tasked, error prone, etc.radio/RF link, etc.

In this regard, and now referring to FIGS. 1 and 2, block diagrams of anIoT wireless communication environment (100) comprising an RF fidelitylayer of an IoT wireless device and an RF fidelity component of a hostsystem; and an end-to-end TCP stack (200) within the IoT wirelesscommunication environment are illustrated, respectively, in accordancewith various example embodiments.

In embodiment(s), IoT wireless device 110 can comprise, e.g., a sensor,a meter, a utility (e.g., water, gas, electricity, etc.) meter, a radiofrequency identification (RFID) device, a machine-to-machine (M2M) baseddevice, a wireless and/or wired device, an appliance sensor, a securitysensor, a motion sensor, a camera, a health monitor device, a fitnesstracking device, a smartwatch, a home security system device, athermostat, a smartphone, a laptop device, a tablet device, a televisiondevice, a vehicle device, a gaming console device, a user equipment(UE), a power and/or energy control device, an industrial control and/ormonitoring device, etc.

In one embodiment, IoT wireless device 110 can be a uniquelyidentifiable embedded computing device, e.g., assigned a unique IPaddress, and IoT device application 202 can exchange information and/orperform actions (e.g., remote monitoring, remote control, etc.) usinginformation, network communications, data, etc. transferred, viawireless network 120, between the IoT wireless device 110 andapplication(s), e.g., host application 242, of host system 130.

In this regard, IoT wireless device 110 can be communicatively coupledto host system 130, via wireless interface 102, utilizing access point(AP) 122, e.g., a macro AP, a Femto AP, a pico AP, a base station, etc.Wireless interface 102 can comprise an over-the-air wireless linkcomprising a downlink (DL) and an uplink (UL) (both not shown) that canutilize a predetermined band of radio frequency (RF) spectrum associatedwith, e.g., cellular, LTE, LTE advanced (LTE-A), GSM, 3GPP universalmobile telecommunication system (UMTS), Institute of Electrical andElectronics Engineers (IEEE) 802.XX technology (WiFi, Bluetooth, etc.),worldwide interoperability for microwave access (WiMax), a wirelesslocal area network (WLAN), Femto, near field communication (NFC),Wibree, Zigbee, satellite, WiFi Direct, etc. Accordingly, wirelessnetwork 120 can be associated with RF spectrums corresponding torespective types of wireless technologies including, but not limited to,cellular, WiFi, WiMax, WLAN, Femto, NFC, Wibree, Zigbee, satellite, WiFiDirect, etc.

Referring now to FIG. 2, in an embodiment, component(s), logic, etc. ofRF fidelity layer 112 can be implemented within respective portion(s),layer(s), etc. of a protocol stack, network protocol suite, etc. of IoTwireless device 110, e.g., between IoT device application 202 andtransport layer 204 (e.g., comprising TCP functionality), which isbetween RF fidelity layer 112 and internet layer 206, data link layer208, and physical layer 210. Accordingly, IoT device application 202 can“send and fire” data, data packets, communications, etc. (i.e., fortransmission to host system 130) to transport layer 204—without havingknowledge, awareness, etc. of function(s), operation(s), etc. beingperformed by RF fidelity layer 112.

In this regard, such function(s), operation(s), etc. being performed byRF fidelity layer 112 can comprise determining a characteristic, e.g.,RSSI, BER, RSRP, RSRQ, SINR, BLER, bit throughput, etc. of an RF channelthat couples, via wireless interface 102, IoT wireless device 110 to AP122—AP 122 being configured to transfer, e.g., via intermediate system230, data between IoT wireless device 110 and host system 130, e.g., ahome security system, a home automation system, a building monitorsystem, a building control system, etc. to facilitate furtherprocessing, evaluation, etc. of such data by host application 242.

In an embodiment, RF fidelity layer 112 can determine the characteristicof the RF channel by sending control command(s), e.g., AT command(s), toa radio module, e.g., LTE radio module 730 (see below) of IoT wirelessdevice 110 to obtain the characteristic, e.g., via communication(s),register(s), memory location(s), etc. of the radio module.

In other embodiment(s), RF fidelity layer 112 can obtain thecharacteristic of the RF channel via probe(s), mechanism(s), etc. notexposed through the AT command(s). For instance, the characteristic,information, etc. associated with the RF channel, radio module, etc. canbe collected via other control command(s), method(s), etc., or viadirect monitoring of RF and/or data signals. Additionally, otherinformation collected by RF fidelity layer 112 can comprise informationabout: IoT wireless device 110, a corresponding system, e.g., AP 122,and/or a corresponding environment, e.g., information comprising systemantenna capability (e.g., IoT wireless device 110 antenna capability, AP122 antenna capability, etc.); link loading; reduced power (e.g.,reduced system power, reduced IoT wireless device 110 power, etc.); amobility speed; a density of surrounding cell sites; an IoT wirelessdevice 110 battery state, etc.

In another embodiment, the RF channel can comprise a data channel and acontrol channel; and RF fidelity layer 112 can monitor, determine, etc.the characteristic of the control channel based on controlmessages/communications that have been communicated between IoT wirelessdevice 110 and AP 122. In this regard, since the controlmessages/communications utilize wireless resources, device resources,etc. of IoT wireless device 110 that are the same and/or similar toresources utilized to send, communicate, etc., via the data channel,data messages/communications to host system 130, RF fidelity layer 112can probe, determine, monitor, etc. characteristic(s) of the RF channelvia the control channel, without artificially sending data packets,extra data packets, test packets, etc. from IoT wireless device 110 toAP 122 using the data channel, e.g., without incurring extra datacharges related to sending, communicating, etc. datamessages/communications to host system 130 via AP 122.

In yet another embodiment(s), RF fidelity layer 112 can probe,determine, monitor, etc. characteristic(s) of the RF channel byobtaining information from portion(s), layer(s), etc. of a protocolstack, network protocol suite, etc. of IoT wireless device 110; and/orby obtaining information from devices, sensors, etc. of wireless device,etc. In this regard, such information can comprise: a determined amountof MAC retransmissions that have occurred within a defined period oftime; an availability of access points near, in communication with, etc.wireless IoT device 110; a link loading corresponding to data packettransfers within the portion(s), layer(s), etc. of the protocol stack,network protocol suite, etc.; a transmission power of IoT wirelessdevice 110; a mobility speed (e.g., rate of movement) of IoT wirelessdevice, e.g., represented by a number of handoffs that have beendetermined to have occurred within a defined period of time; an antennacapability (e.g., single, multiple-input multiple-output (MIMO), etc.)of IoT wireless device 110, an amount of RF interference, e.g., whichhas been determined to have occurred within a defined period of time,etc.

In turn, in response to a determination that the monitored, probed, etc.characteristic of the RF channel satisfies a defined conditionrepresenting a degradation of a fidelity of the RF channel, RF fidelitylayer 112 can tune, modify, preempt, limit, reduce, withhold, delay,etc.—based on a determined classification (e.g.,critical/urgent/priority, non-critical/non-urgent/non-priority/normal,control, maintenance, update, standby, etc.) of outbound data that hasbeen received from IoT device application 202 to be transmitted to hostsystem 130—a transmission of the outbound data to host system 130.

In this regard, in response to a determination that the fidelity of theRF channel is poor, lossy, error prone, degraded, etc., RF fidelitylayer 112 can maximize throughput of data, communications, etc. thathave been classified as critical/urgent/priority, and reduce consumptionof network device bandwidth corresponding to retransmission of data thathas been classified as non-critical/non-urgent/non-priority/normal,control, etc. by enabling, allowing, permitting, etc. transmission ofthe data that has been classified as critical/urgent/priority, whilelimiting, reducing, withholding, delaying, etc. transmission of the datathat has been classified as non-critical/non-urgent/non-priority/normal,control, etc.

In an embodiment, RF fidelity layer 112 can limit, reduce, withhold,delay, etc. the transmission of the outbound data that has beenclassified as non-critical/non-urgent/non-priority/normal, control, etc.until characteristic(s) of the RF channel have been determined toimprove. In another embodiment, RF fidelity layer 112 can limit, reduce,withhold, delay, etc. the transmission of outbound data that has beenclassified as non-critical/non-urgent/non-priority/normal, control, etc.for a defined period of time, defined delay period, etc.

In one embodiment, RF fidelity layer 112 can comprise a memory, buffers,FIFO buffers, etc. (not shown) to facilitate collection of the outbounddata that has been classified asnon-critical/non-urgent/non-priority/normal, control, etc., andfacilitate a later transmission of such stored, buffered, etc. data fromwireless device 110, e.g., based on a determination that thecharacteristics of the RF channel have improved after a defined periodof time, delay period, etc.

In another embodiment illustrated by FIG. 3, component(s), logic, etc.of RF fidelity layer 112 can be implemented, integrated, etc. within IoTdevice application 202. In this regard, IoT device application 202 canperform functions, operations, etc. described herein with respect to,e.g., limiting, reducing, withholding, delaying, etc. the transmissionof outbound data to host system 130 that has been classified asnon-critical/non-urgent/non-priority/normal, control, etc.

In yet another embodiment illustrated by FIG. 4, component(s), logic,etc. of RF fidelity 112 can be implemented as a device library, e.g., adynamic linked library (DLL), which can be accessed from IoT deviceapplication 202. In this regard, IoT device application 202 can perform,via the DLL, functions, operations, etc. described herein with respectto, e.g., limiting, reducing, withholding, delaying, etc. thetransmission of outbound data to host system 130 that has beenclassified as non-critical/non-urgent/non-priority/normal, control, etc.by executing/calling functions of the DLL.

Now referring to FIG. 2, RF fidelity component 132 of host system 130can probe, determine, monitor, etc. characteristic(s) of the RF channel;and in response to the characteristic(s) of the RF channel beingdetermined to satisfy a defined condition representing a degradation ofa fidelity of the RF channel, RF fidelity component 132 can modify,based on a priority level of outgoing data that has been directed fromhost application 242 to IoT wireless device 110, a transmission of theoutgoing data, e.g., to facilitate a reduction of wirelessretransmissions of the outgoing data due to the degradation of thefidelity of the RF channel.

In embodiment(s), host system 130 can comprise a home security system, ahome automation system, a building monitor system, a building controlsystem, etc. In turn, host application 242 can send/receive data, viaintermediate system 230 and wireless network 102, to/from IoT wirelessdevice 110 to facilitate processing, by host application 242 based onthe data, information corresponding to home security, automation,control, etc. In embodiment(s), host system 130 can be communicativelycoupled to intermediate system 230 utilizing one or more of the Internet(or another communication network (e.g., an Internet protocol (IP) basednetwork)), a digital subscriber line (DSL)-type or broadband networkfacilitated by Ethernet or other technology, and/or wirelessinterface(s), e.g., cellular, WiFi, WiMax, WLAN, Femto, NFC, Wibree,Zigbee, satellite, WiFi Direct, etc. In this regard, components,portions(s, etc. of IoT communication environment 100 can comprise acloud-based, centralized, communication platform, Internet platform,WAN, etc. (see, e.g., 1590 below), and component(s), portion(s), etc. ofhost system 130 can be implemented within the cloud-based, centralized,communication platform.

In an embodiment, component(s), logic, etc. of RF fidelity component 132can be implemented within respective portion(s), layer(s), etc. of aprotocol stack, network protocol suite, etc. of host system 130, e.g.,between host application 242 and transport layer 244 (e.g., comprisingTCP functionality), which is between RF fidelity component 132 andinternet layer 246, data link layer 248, and physical layer 250.Accordingly, host application 242 can “send and fire” data, datapackets, communications, etc. (i.e., for transmission to IoT wirelessdevice 110) to transport layer 244—without having knowledge, awareness,etc. of function(s), operation(s), etc. being performed by RF fidelitycomponent 132.

In this regard, such function(s), operations(s), etc. being performed byRF fidelity component 132 can comprise determining, predicting, etc. afidelity of the RF channel based on an analysis, evaluation, etc. ofinbound data that has been received from IoT wireless device 110. Forexample, RF fidelity component 132 can determine whether data,communications, etc. that have been received from IoT wireless device110 satisfy a defined condition representing the fidelity of the RFchannel is poor, lossy, error prone, degraded, etc.

In one embodiment, RF fidelity component 132 can determine whether amajority of incoming communications that have been received from IoTwireless device 110, e.g., over a defined period, have been classifiedas critical/urgent/priority, e.g., instead of comprising a mix ofclassifications, e.g., critical/urgent/priority,non-critical/non-urgent/non-priority/normal, control, etc.

In turn, in response to determining that a majority of the incomingcommunications that have been received from IoT wireless device 110 havebeen classified as critical/urgent/priority, e.g., without comprisingthe mix of classifications, RF fidelity component 132 can infer,determine, etc. that the fidelity of the RF channel is poor, lossy,error prone, degraded, etc. Further, based on the determination that thefidelity of the RF channel is poor, lossy, error prone, degraded, etc.,RF fidelity component 132 can withhold, delay, filter, limit, etc. atransmission of data, which has been received from host application 242,to IoT wireless device 110. In this regard, in embodiment(s), RFfidelity component 132 can enable transmission ofcritical/urgent/priority data to IoT wireless device 110 during poor,lossy, error prone, degraded, etc. wireless conditions, whilewithholding, delaying, etc. transmission of data classified asnon-critical/non-urgent/non-priority/normal, control, etc. under suchconditions.

For example, in one embodiment, in response to a classification of anincoming communication from IoT wireless device 110 being determined tosatisfy a defined condition with respect to an amount ofcritical/urgent/priority communications that have been received from IoTwireless device 110 during a defined period, e.g., representing that amajority of incoming communications that have been received over thedefined period have been classified as critical/urgent/priority, RFfidelity component 132 can withhold, delay, etc. a transmission of anon-critical/non-urgent/non-priority/normal, control, etc.data/communication that has been directed to IoT wireless device 110.

In another embodiment, in response to the characteristic of the RFchannel being determined to satisfy a defined condition representing animprovement of the fidelity of the RF channel, e.g., representing that amajority of incoming communications that have been received from IoTwireless device 110 over the defined period have been classified asnon-critical/non-urgent/non-priority/normal, control, etc., RF fidelitycomponent 132 can transmit, send, etc. (e.g., without limiting,withholding, delaying, etc.) thenon-critical/non-urgent/non-priority/normal, control, etc. communicationdirected to IoT wireless device 110.

In yet another embodiment, in response to the classification of theincoming communication being determined to satisfy the defined conditionwith respect to the amount of priority communications that have beenreceived during the defined period, e.g., representing that the majorityof the incoming communications that have been received over the definedperiod have been classified as critical/urgent/priority, RF fidelitycomponent 132 can transmit, send, etc. (e.g., without limiting,withholding, delaying etc.) critical/urgent/prioritydata/communication(s) directed to IoT wireless device 110.

In an embodiment, RF fidelity component 132 can determine the fidelityof the RF channel based on information that has been appended todata/communications that have been received from IoT wireless device110. In this regard, in response to a determination, by RF fidelitylayer 112 of IoT wireless device 110, that a characteristic of the RFchannel satisfies a defined condition representing that the fidelity ofthe RF channel is poor, lossy, error prone, degraded, etc., RF fidelitylayer 112 can append information representing that the fidelity of theRF channel has been determined to be poor, error prone, degraded, etc.to existing data/communications readied to be sent to the host system130. In embodiment(s), the appended information can represent an RSSI,BER, RSRP, RSRQ, SINR, BLER, bit throughput, etc. corresponding to theRF channel.

In turn, upon receipt of the data/communications comprising the appendedinformation, RF fidelity component 132 can remove, strip, etc. theappended information from the data/communications to obtain applicationdata, and forward the application data to host application 242 tofacilitate further processing of the application data by hostapplication 242.

Further, in response to a determination, based on the appendedinformation, that the fidelity of the RF channel is poor, lossy, errorprone, degraded, etc., RF fidelity component 132 can filter, limit, etc.transmission(s) of communications/data that have been received from hostapplication 242 and directed to IoT wireless device 110, e.g., enablingtransmissions of critical/urgent/priority data to IoT wireless device110, while preventing, withholding, etc. transmissions ofnon-critical/non-urgent/non-priority/normal, control, etc. data to IoTwireless device 110.

In this regard, in another embodiment, in response to a determination,based on the appended information, that the fidelity of the RF channelis poor, lossy, error prone, degraded, etc., RF fidelity component 132can send, transmit, etc. (e.g., without withholding, delaying, etc.)communications/data that have been classified ascritical/urgent/priority directed to IoT wireless device 110.

In one embodiment, RF fidelity component 132 can comprise a memory,buffers, FIFO buffers, etc. (not shown) to facilitate collection of thedata that has been received from host application 242 for transmissionto IoT wireless device 110, and that has been determined to beclassified as non-critical/non-urgent/non-priority/normal, control,etc.—such stored, buffered, etc. data being transmitted to wirelessdevice 110 upon a determination, e.g., after a defined period of time,delay period, etc. that the characteristics of the RF channel haveimproved.

In another embodiment illustrated by FIG. 5, component(s), logic, etc.of RF fidelity component 132 can be implemented, integrated, etc. withinhost application 242. In this regard, host application 242 can performfunctions, operations, etc. described herein with respect to, e.g.,limiting, reducing, withholding, delaying, etc. the transmission of datathat has been directed to IoT wireless device 110 and classified asnon-critical/non-urgent/non-priority/normal, control, etc.

In yet another embodiment illustrated by FIG. 6, component(s), logic,etc. of RF fidelity component 132 can be implemented as a devicelibrary, e.g., a DLL, which can be accessed from host application 242.In this regard, host application 242 can perform, e.g., byexecuting/calling functions of the DLL, operations described herein withrespect to, e.g., limiting, reducing, withholding, delaying, etc. thetransmission of data that has been directed to IoT wireless device 110and that has been classified asnon-critical/non-urgent/non-priority/normal, control, etc.

Now referring to FIG. 7, a block diagram (700) of an IoT wireless devicecomprising RF fidelity layer 112 is illustrated, in accordance withvarious embodiments. Processing component 710 can send/receiveinformation to/from input/output (I/O) sensors/actuators 710. Inembodiment(s), I/O sensors/actuators 710 can comprise a sensor, a meter,a utility (e.g., water, gas, electricity, etc.) meter, an RFID device,an M2M based device, a wireless and/or wired device, an appliancesensor, a security sensor, a motion sensor, a camera, a health monitordevice, a fitness tracking device, a smartwatch, a home security systemdevice, a thermostat, a smartphone, a laptop device, a tablet device, atelevision device, a vehicle device, a gaming console device, a UE, apower and/or energy control device, an industrial control and/ormonitoring device, etc. In this regard, processing component 710 cansend, via a radio/RF link (e.g., 102) coupled to LTE radio module 730using antenna(s) 740, information obtained from I/O sensors/actuators710 directed to host device 130, e.g., to facilitate further processingof the information by host application 242.

Further, processing component 720 can comprise RF fidelity layer 112,which can probe, determine, monitor, etc. characteristic(s) of aradio/RF link (e.g., 102), e.g., corresponding to a control channel,between IoT wireless device 110 and AP 122. In this regard, RF fidelitylayer 112 can probe, determine, monitor, etc. the characteristic(s) ofthe radio/RF link by sending, via interface 725, AT command(s) to LTEradio module 730.

In turn, based on the AT command(s), LTE radio module 730 can provide,e.g., via interface 725 and/or registers, memory locations, etc. (notshown), the characteristics(s) (e.g., RSSI, BER, RSRP, RSRQ, SINR, BLER,a bit throughput, etc. of the radio/RF link) to processing component 720and/or RF fidelity layer 112.

In other embodiment(s), RF fidelity layer 112 can obtain thecharacteristic(s) via probe(s), mechanism(s), etc. not exposed throughthe AT command(s). For instance, the characteristic(s) can be collectedvia other control command(s), method(s), etc., or via direct monitoringof RF and/or data signals. Additionally, other information collected byRF fidelity layer 112 can comprise information about IoT wireless device110 and/or AP 122, e.g., IoT wireless device antenna capability, AP 122antenna capability, etc.; link loading; reduced power (e.g., reduced AP122 power, reduced IoT wireless device 110 power, etc.); mobility speed,e.g., of IoT wireless device 110; a density of surrounding cell sites,e.g., a density of cell sites surrounding, within a predetermineddistance, etc. of IoT wireless device 110; a battery state of IoTwireless device 110, etc.

FIGS. 8-14 illustrate methodologies in accordance with the disclosedsubject matter. For simplicity of explanation, the methodologies aredepicted and described as a series of acts. It is to be understood andappreciated that various embodiments disclosed herein are not limited bythe acts illustrated and/or by the order of acts. For example, acts canoccur in various orders and/or concurrently, and with other acts notpresented or described herein. Furthermore, not all illustrated acts maybe required to implement the methodologies in accordance with thedisclosed subject matter. In addition, those skilled in the art willunderstand and appreciate that the methodologies could alternatively berepresented as a series of interrelated states via a state diagram orevents. Additionally, it should be further appreciated that themethodologies disclosed hereinafter and throughout this specificationare capable of being stored on an article of manufacture to facilitatetransporting and transferring such methodologies to computers. The termarticle of manufacture, as used herein, is intended to encompass acomputer program accessible from any computer-readable device, carrier,or media.

Referring now to FIGS. 8-10, processes 800-1000 performed by an IoTwireless device (e.g., 110) comprising RF fidelity layer 112 areillustrated, in accordance with various example embodiments. At 810, RFfidelity layer 112 can determine a characteristic of an RF channelwirelessly coupling the IoT wireless device to an AP device that hasbeen configured to transmit data that has been received from the IoTwireless device to a host device (e.g., 130) to facilitate furtherprocessing of the data by an application (e.g., 242) executing on thehost device.

At 820, RF fidelity layer 112 can determine whether the characteristicof the RF channel satisfies a defined condition representing a fidelityof the RF channel has degraded. In turn, if the characteristic of the RFchannel has been determined to satisfy the defined conditionrepresenting the fidelity of the RF channel has degraded, flow continuesto 910, at which RF fidelity layer 112 can determine whether a pendingtransmission of data has been classified as a critical/urgent/prioritytransmission; otherwise flow returns to 810.

At 910, in response to a determination that the pending transmission hasbeen classified as a critical/urgent/priority transmission, flowcontinues from 910 to 920, at which RF fidelity layer 112 can facilitatea transmission, by the IoT wireless device, of the data directed to thehost device; otherwise flow continues to 930, at which RF fidelity layer112 can facilitate a delay, by the IoT wireless device, of atransmission of the data to the host device.

Flow continues from 930 to 1010, at which RF fidelity layer 112 canfacilitate a redetermination of the characteristic of the RF channel.From 1010, flow continues to 1020, at which RF fidelity layer 112 candetermine whether the characteristic satisfies a defined conditionrepresenting that the fidelity of the RF channel has improved. In thisregard, in response to a determination that the characteristic satisfiesthe defined condition representing that the fidelity of the RF channelhas improved, flow continues to 1030, at which RF fidelity layer 112 canfacilitate a transmission, by the IoT wireless device, of the datadirected to the host device; otherwise flow returns to 1010.

FIGS. 11-14 illustrate flowcharts of methods associated with a hostsystem (e.g., 130) comprising RF fidelity component 132, in accordancewith various embodiments. At 1110, RF fidelity component 132 candetermine, based on communications that have been received from awireless device (e.g., 110), a fidelity of an RF channel wireles slycoupling the wireless device to an AP device that has been configured totransmit the communications to the system to facilitate furtherprocessing of the communications by an application (e.g., 242) executingon the system.

At 1120, RF fidelity component 132 can determine whether a fidelity ofthe RF channel is degraded. In this regard, in response to adetermination that the fidelity of the RF channel is degraded, flowcontinues to 1210, at which RF fidelity component 132 can determinewhether a communication/data that has been received from hostapplication 242 and that is readied for transmission to the wirelessdevice has been classified as a critical/urgent/prioritycommunication/data; otherwise flow returns to 1110.

At 1210, if it is determined that the communication/data that has beenreceived from host application 242 and that is readied for transmissionto the wireless device has been classified as thecritical/urgent/priority, etc. communication/data, flow continues to1220, at which RF fidelity component can facilitate a transmission, bythe host system, of the communication/data directed to the wirelessdevice; otherwise flow continues to 1230, at which RF fidelity componentcan facilitate a delay, by the system, of the transmission of thecommunication/data.

Flow continues from 1230 to 1310, at which RF fidelity component 132 canre-determine, based on the communications that have been received fromthe wireless device, the fidelity of the RF channel. At 1320, inresponse to a determination that the fidelity of the RF channel hasimproved, flow continues to 1330, at which RF fidelity component 132 canfacilitate a transmission, by the system, of the communication/datadirected to the wireless device; otherwise flow returns to 1310.

Now referring to FIG. 14, a flowchart of a method associated with a hostsystem (e.g., 130) comprising RF fidelity component 132 for determininga fidelity of an RF channel based on information that has been appendedto a communication is illustrated, in accordance with variousembodiments. At 1410, RF fidelity component 132 can determine, based oninformation that has been appended to a communication that has beenreceived from a wireless device (e.g., 110), a fidelity of an RF channelwirelessly coupling the wireless device to an AP device that has beenconfigured to transmit the communication to the system to facilitatefurther processing of the communication by an application (e.g., 242)that has been executing on the system.

At 1420, RF fidelity component 132 can strip, remove, etc. theinformation from the communication as appended information, and forwardthe communication to the application. At 1430, in response to adetermination, by RF fidelity component 132 based on the appendedinformation, that the fidelity of the RF channel is degraded, poor,lossy, etc., RF fidelity component 132 can facilitate filtering,delaying, withholding, etc. transmissions of respective communicationsfrom the system to the wireless device.

With respect to FIG. 15, a wireless communication environment 1500including macro network platform 1510 is illustrated, in accordance withvarious embodiments. Macro network platform 1510 serves or facilitatescommunication with an IoT device, sensor, wireless device (e.g., 110)and host system 130 via wireless network 120. It should be appreciatedthat in cellular wireless technologies, e.g., 3GPP UMTS, high speedpacket access (HSPA), 3GPP LTE, third generation partnership project 2(3GPP2), ultra mobile broadband (UMB), LTE-A, etc. that can beassociated with wireless network 120, macro network platform 1510 can beembodied in a core network. It is noted that wireless network 120 caninclude base station(s) (e.g., 122), base transceiver station(s), accesspoint(s), etc. and associated electronic circuitry and deploymentsite(s), in addition to a wireless radio link (e.g., 102) operated inaccordance with the base station(s), etc. Accordingly, wireless network120 can comprise various coverage cells, or wireless coverage areas. Inaddition, it should be appreciated that elements and/or components ofhost system 130 can be located/included within one or morecomponents/elements, e.g., hardware, software, etc., of wirelesscommunication environment 1500, e.g., macro network platform 1510,cloud-based communication platform 1590, etc.

Generally, macro network platform 1510 includes components, e.g., nodes,GWs, interfaces, servers, platforms, etc. that facilitate bothpacket-switched (PS), e.g., IP, frame relay, asynchronous transfer mode(ATM), and circuit-switched (CS) traffic, e.g., voice and data, andcontrol generation for networked wireless communication, e.g., via hostsystem 130. In various embodiments, macro network platform 1510 includesCS gateway (GW) node(s) 1512 that can interface CS traffic received fromlegacy networks like telephony network(s) 1540, e.g., public switchedtelephone network (PSTN), public land mobile network (PLMN), SignallingSystem No. 7 (SS7) network 1560, etc. CS GW node(s) 1512 can authorizeand authenticate traffic, e.g., voice, arising from such networks.Additionally, CS GW node(s) 1512 can access mobility or roaming datagenerated through SS7 network 1560; for instance, mobility data storedin a visitor location register (VLR), which can reside in memory 1530.Moreover, CS GW node(s) 1512 interfaces CS-based traffic and signalingwith PS GW node(s) 1518. As an example, in a 3GPP UMTS network, PS GWnode(s) 1518 can be embodied in GW general packet radio service (GPRS)support node(s) (GGSN).

As illustrated by FIG. 15, PS GW node(s) 1518 can receive and processCS-switched traffic and signaling via CS GW node(s) 1512. Further PS GWnode(s) 1518 can authorize and authenticate PS-based data sessions,e.g., via wireless network 120, with served devices, communicationdevices, etc. Such data sessions can include traffic exchange withnetworks external to macro network platform 1510, like wide areanetwork(s) (WANs) 1550; enterprise networks (NWs) 1570, e.g., E911,service NW(s) 1580, e.g., an IP multimedia subsystem (IMS), etc. Itshould be appreciated that local area network(s) (LANs), which may be apart of enterprise NW(s) 1570, can also be interfaced with macro networkplatform 1510 through PS GW node(s) 1518. PS GW node(s) 1518 cangenerate packet data contexts when a data session is established, e.g.,associated with an EPS bearer context activation. To that end, in anaspect, PS GW node(s) 1518 can include a tunnel interface, e.g., tunneltermination GW (TTG) in 3GPP UMTS network(s) (not shown), which canfacilitate packetized communication with disparate wireless network(s),such as Wi-Fi networks. It should be further appreciated that thepacketized communication can include multiple flows that can begenerated through server(s) 1514. It is to be noted that in 3GPP UMTSnetwork(s), PS GW node(s) 1518 (e.g., GGSN) and tunnel interface (e.g.,TTG) comprise a packet data GW (PDG).

Macro network platform 1510 also includes serving node(s) 1516 that canconvey the various packetized flows of information, or data streams,received through PS GW node(s) 1518. As an example, in a 3GPP UMTSnetwork, serving node(s) can be embodied in serving GPRS support node(s)(SGSN).

As indicated above, server(s) 1514 in macro network platform 1510 canexecute numerous applications, e.g., messaging, location services,wireless device management, etc. that can generate multiple disparatepacketized data streams or flows; and can manage such flows, e.g.,schedule, queue, format. Such application(s), for example can includeadd-on features to standard services provided by macro network platform1510. Data streams can be conveyed to PS GW node(s) 1518 forauthorization/authentication and initiation of a data session, and toserving node(s) 1516 for communication thereafter. Server(s) 1514 canalso effect security, e.g., implement one or more firewalls, of macronetwork platform 1510 to ensure network's operation and data integrityin addition to authorization and authentication procedures that CS GWnode(s) 1512 and PS GW node(s) 1518 can enact. Moreover, server(s) 1514can provision services from external network(s), e.g., WAN 1550, orglobal positioning system (GPS) network(s), which can be a part ofenterprise NW(s) 1580. It is to be noted that server(s) 1514 can includeone or more processors configured to confer at least in part thefunctionality of macro network platform 1510. To that end, the one ormore processors can execute code instructions stored in memory 1530, forexample.

In wireless communication environment 1500, memory 1530 can storeinformation related to operation of macro network platform 1510, e.g.,related to operation of IoT wireless device 110, host system 130, etc.The information can include business data associated with subscribers;market plans and strategies, e.g., promotional campaigns, businesspartnerships, mobile devices served through macro network platform,etc.; service and privacy information, policies, etc.; end-user servicelogs for law enforcement; term(s) and/or condition(s) associated withwireless service(s) provided via wireless network 120; and so forth.Memory 1530 can also store information from at least one of telephonynetwork(s) 1540, WAN 1550, SS7 network 1560, enterprise NW(s) 1570, orservice NW(s) 1580.

In one or more embodiments, components of core network environment 1500can provide, e.g., via cloud-based communication platform 1590,communication services to IoT wireless device 110 and host system 130utilizing an over-the-air wireless link, e.g., 102, via wireless network120. In this regard, wireless network 120 can include one or more:macro, Femto, or pico access points (APs) (not shown); base stations(BS) (not shown); landline networks (e.g., optical landline networks,electrical landline networks) (not shown) communicatively coupledbetween IoT wireless device 110 and macro network platform 1510.

Core network environment 1500 can include one or more of the Internet(or another communication network (e.g., IP-based network)), or DSL-typeor broadband network facilitated by Ethernet or other technology. Invarious embodiments, core network environment 1500 can include hardwareand/or software for allocating resources to IoT wireless device 110 andhost system 130, converting or enforcing protocols, establishing and/orproviding levels of quality of service (QoS), providing applications orservices, translating signals, and/or performing other desired functionsto facilitate system interoperability and communication to/from IoTwireless device 110 and host system 130.

In other embodiment(s), core network environment 1500 can include datastore component(s), a memory configured to store information,computer-readable storage media storing computer-executableinstructions, e.g., memory 1530, etc. enabling various operationsperformed via host system 130 as described herein.

As it employed in the subject specification, the term “processor” canrefer to substantially any computing processing unit or devicecomprising, but not limited to comprising, single-core processors;single-processors with software multithread execution capability;multi-core processors; multi-core processors with software multithreadexecution capability; multi-core processors with hardware multithreadtechnology; parallel platforms; and parallel platforms with distributedshared memory. Additionally, a processor can refer to an integratedcircuit, an application specific integrated circuit (ASIC), a digitalsignal processor (DSP), a field programmable gate array (FPGA), aprogrammable logic controller (PLC), a complex programmable logic device(CPLD), a discrete gate or transistor logic, discrete hardwarecomponents, or any combination thereof designed to perform the functionsand/or processes described herein. Processors can exploit nano-scalearchitectures such as, but not limited to, molecular and quantum-dotbased transistors, switches and gates, in order to optimize space usageor enhance performance of mobile devices. A processor may also beimplemented as a combination of computing processing units.

In the subject specification, terms such as “store,” “data store,” “datastorage,” “database,” “memory storage,” and substantially any otherinformation storage component relevant to operation and functionality ofa component and/or process, refer to “memory components,” or entitiesembodied in a “memory,” or components comprising the memory. It will beappreciated that the memory components described herein can be eithervolatile memory or nonvolatile memory, or can include both volatile andnonvolatile memory.

By way of illustration, and not limitation, nonvolatile memory, forexample, can be included in non-volatile memory 1622 (see below), diskstorage 1624 (see below), and/or memory storage 1646 (see below).Further, nonvolatile memory can be included in read only memory (ROM),programmable ROM (PROM), electrically programmable ROM (EPROM),electrically erasable ROM (EEPROM), or flash memory. Volatile memory1620 can include random access memory (RAM), which acts as externalcache memory. By way of illustration and not limitation, RAM isavailable in many forms such as synchronous RAM (SRAM), dynamic RAM(DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM),enhanced SDRAM (ESDRAM), Synchlink DRAM (SLDRAM), and direct Rambus RAM(DRRAM). Additionally, the disclosed memory components of systems ormethods herein are intended to comprise, without being limited tocomprising, these and any other suitable types of memory.

In order to provide a context for the various aspects of the disclosedsubject matter, FIG. 16, and the following discussion, are intended toprovide a brief, general description of a suitable environment in whichthe various aspects of the disclosed subject matter can be implemented.While the subject matter has been described above in the general contextof computer-executable instructions of a computer program that runs on acomputer and/or computers, those skilled in the art will recognize thatvarious embodiments disclosed herein can be implemented in combinationwith other program modules. Generally, program modules include routines,programs, components, data structures, etc. that perform particulartasks and/or implement particular abstract data types.

Moreover, those skilled in the art will appreciate that the inventivesystems can be practiced with other computer system configurations,including single-processor or multiprocessor computer systems, computingdevices, mini-computing devices, mainframe computers, as well aspersonal computers, hand-held computing devices (e.g., PDA, phone,watch), microprocessor-based or programmable consumer or industrialelectronics, and the like. The illustrated aspects can also be practicedin distributed computing environments where tasks are performed byremote processing devices that are linked through a communicationnetwork; however, some if not all aspects of the subject disclosure canbe practiced on stand-alone computers. In a distributed computingenvironment, program modules can be located in both local and remotememory storage devices.

With reference to FIG. 16, a block diagram of a computing system 1600operable to execute the disclosed systems and methods is illustrated, inaccordance with an embodiment. Computer 1612 includes a processing unit1614, a system memory 1616, and a system bus 1618. System bus 1618couples system components including, but not limited to, system memory1616 to processing unit 1614. Processing unit 1614 can be any of variousavailable processors. Dual microprocessors and other multiprocessorarchitectures also can be employed as processing unit 1614.

System bus 1618 can be any of several types of bus structure(s)including a memory bus or a memory controller, a peripheral bus or anexternal bus, and/or a local bus using any variety of available busarchitectures including, but not limited to, industrial standardarchitecture (ISA), micro-channel architecture (MSA), extended ISA(EISA), intelligent drive electronics (IDE), VESA local bus (VLB),peripheral component interconnect (PCI), card bus, universal serial bus(USB), advanced graphics port (AGP), personal computer memory cardinternational association bus (PCMCIA), Firewire (IEEE 1394), smallcomputer systems interface (SCSI), and/or controller area network (CAN)bus used in vehicles.

System memory 1616 includes volatile memory 1620 and nonvolatile memory1622. A basic input/output system (BIOS), containing routines totransfer information between elements within computer 1612, such asduring start-up, can be stored in nonvolatile memory 1622. By way ofillustration, and not limitation, nonvolatile memory 1622 can includeROM, PROM, EPROM, EEPROM, or flash memory. Volatile memory 1620 includesRAM, which acts as external cache memory. By way of illustration and notlimitation, RAM is available in many forms such as SRAM, dynamic RAM(DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM),enhanced SDRAM (ESDRAM), Synchlink DRAM (SLDRAM), Rambus direct RAM(RDRAM), direct Rambus dynamic RAM (DRDRAM), and Rambus dynamic RAM(RDRAM).

Computer 1612 also includes removable/non-removable,volatile/non-volatile computer storage media. FIG. 16 illustrates, forexample, disk storage 1624. Disk storage 1624 includes, but is notlimited to, devices like a magnetic disk drive, floppy disk drive, tapedrive, Jaz drive, Zip drive, LS-100 drive, flash memory card, or memorystick. In addition, disk storage 1624 can include storage mediaseparately or in combination with other storage media including, but notlimited to, an optical disk drive such as a compact disk ROM device(CD-ROM), CD recordable drive (CD-R Drive), CD rewritable drive (CD-RWDrive) or a digital versatile disk ROM drive (DVD-ROM). To facilitateconnection of the disk storage devices 1624 to system bus 1618, aremovable or non-removable interface is typically used, such asinterface 1626.

It is to be appreciated that FIG. 16 describes software that acts as anintermediary between users and computer resources described in suitableoperating environment 1600. Such software includes an operating system1628. Operating system 1628, which can be stored on disk storage 1624,acts to control and allocate resources of computer system 1612. Systemapplications 1630 take advantage of the management of resources byoperating system 1628 through program modules 1632 and program data 1634stored either in system memory 1616 or on disk storage 1624. It is to beappreciated that the disclosed subject matter can be implemented withvarious operating systems or combinations of operating systems.

A user can enter commands or information into computer 1612 throughinput device(s) 1636. Input devices 1636 include, but are not limitedto, a pointing device such as a mouse, trackball, stylus, touch pad,keyboard, microphone, joystick, game pad, satellite dish, scanner, TVtuner card, digital camera, digital video camera, web camera, cellularphone, user equipment, smartphone, and the like. These and other inputdevices connect to processing unit 1614 through system bus 1618 viainterface port(s) 1638. Interface port(s) 1638 include, for example, aserial port, a parallel port, a game port, a universal serial bus (USB),a wireless based port, e.g., WiFi, Bluetooth, etc. Output device(s) 1640use some of the same type of ports as input device(s) 1636.

Thus, for example, a USB port can be used to provide input to computer1612 and to output information from computer 1612 to an output device1640. Output adapter 1642 is provided to illustrate that there are someoutput devices 1640, like display devices, light projection devices,monitors, speakers, and printers, among other output devices 1640, whichuse special adapters. Output adapters 1642 include, by way ofillustration and not limitation, video and sound devices, cards, etc.that provide means of connection between output device 1640 and systembus 1618. It should be noted that other devices and/or systems ofdevices provide both input and output capabilities such as remotecomputer(s) 1644.

Computer 1612 can operate in a networked environment using logicalconnections to one or more remote computers, such as remote computer(s)1644. Remote computer(s) 1644 can be a personal computer, a server, arouter, a network PC, a workstation, a microprocessor based appliance, apeer device, or other common network node and the like, and typicallyincludes many or all of the elements described relative to computer1612.

For purposes of brevity, only a memory storage device 1646 isillustrated with remote computer(s) 1644. Remote computer(s) 1644 islogically connected to computer 1612 through a network interface 1648and then physically and/or wirelessly connected via communicationconnection 1650. Network interface 1648 encompasses wire and/or wirelesscommunication networks such as local-area networks (LAN) and wide-areanetworks (WAN). LAN technologies include fiber distributed datainterface (FDDI), copper distributed data interface (CDDI), Ethernet,token ring and the like. WAN technologies include, but are not limitedto, point-to-point links, circuit-switching networks like integratedservices digital networks (e.g., ISDN) and variations thereon, packetswitching networks, and digital subscriber lines (DSL).

Communication connection(s) 1650 refer(s) to hardware/software employedto connect network interface 1648 to bus 1618. While communicationconnection 1650 is shown for illustrative clarity inside computer 1612,it can also be external to computer 1612. The hardware/software forconnection to network interface 1648 can include, for example, internaland external technologies such as modems, including regular telephonegrade modems, cable modems and DSL modems, wireless modems, ISDNadapters, and Ethernet cards.

The computer 1612 can operate in a networked environment using logicalconnections via wired and/or wireless communications to one or moreremote computers, cellular based devices, user equipment, smartphones,or other computing devices, such as workstations, server computers,routers, personal computers, portable computers, microprocessor-basedentertainment appliances, peer devices or other common network nodes,etc. The computer 1612 can connect to other devices/networks by way ofantenna, port, network interface adaptor, wireless access point, modem,and/or the like.

The computer 1612 is operable to communicate with any wireless devicesor entities operatively disposed in wireless communication, e.g., aprinter, scanner, desktop and/or portable computer, portable dataassistant, communications satellite, user equipment, cellular basedevice, smartphone, any piece of equipment or location associated with awireles sly detectable tag (e.g., scanner, a kiosk, news stand,restroom), and telephone. This includes at least WiFi and Bluetoothwireless technologies. Thus, the communication can be a predefinedstructure as with a conventional network or simply an ad hoccommunication between at least two devices.

WiFi allows connection to the Internet from a desired location (e.g., avehicle, couch at home, a bed in a hotel room, or a conference room atwork, etc.) without wires. WiFi is a wireless technology similar to thatused in a cell phone that enables such devices, e.g., mobile phones,computers, etc., to send and receive data indoors and out, anywherewithin the range of a base station. WiFi networks use radio technologiescalled IEEE 802.11 (a, b, g, etc.) to provide secure, reliable, fastwireless connectivity. A WiFi network can be used to connect devices(e.g., mobile phones, computers, etc.) to each other, to the Internet,and to wired networks (which use IEEE 802.3 or Ethernet). WiFi networksoperate in the unlicensed 2.4 and 5 GHz radio bands, at an 11 Mbps(802.11a) or 54 Mbps (802.11b) data rate, for example, or with productsthat contain both bands (dual band), so the networks can providereal-world performance similar to the basic 10BaseT wired Ethernetnetworks used in many offices.

As utilized herein, terms “component,” “system,” “server,” “interface,”and the like are intended to refer to a computer-related entity,hardware, software (e.g., in execution), and/or firmware. For example, acomponent can be a processor, a process running on a processor, anobject, an executable, a program, a storage device, and/or a computer.By way of illustration, an application running on a server and theserver can be a component. One or more components can reside within aprocess, and a component can be localized on one computer and/ordistributed between two or more computers.

Aspects of systems, apparatus, and processes explained herein canconstitute machine-executable instructions embodied within a machine,e.g., embodied in a computer readable medium (or media) associated withthe machine. Such instructions, when executed by the machine, can causethe machine to perform the operations described. Additionally, systems,processes, process blocks, etc. can be embodied within hardware, such asan application specific integrated circuit (ASIC) or the like. Moreover,the order in which some or all of the process blocks appear in eachprocess should not be deemed limiting. Rather, it should be understoodby a person of ordinary skill in the art having the benefit of theinstant disclosure that some of the process blocks can be executed in avariety of orders not illustrated.

Further, components can execute from various computer readable mediahaving various data structures stored thereon. The components cancommunicate via local and/or remote processes such as in accordance witha signal having one or more data packets (e.g., data from one componentinteracting with another component in a local system, distributedsystem, and/or across a network, e.g., the Internet, with other systemsvia the signal).

As another example, a component can be an apparatus with specificfunctionality provided by mechanical parts operated by electric orelectronic circuitry; the electric or electronic circuitry can beoperated by a software application or a firmware application executed byone or more processors; the one or more processors can be internal orexternal to the apparatus and can execute at least a part of thesoftware or firmware application. As yet another example, a componentcan be an apparatus that provides specific functionality throughelectronic components without mechanical parts; the electroniccomponents can include one or more processors therein to executesoftware and/or firmware that confer(s), at least in part, thefunctionality of the electronic components.

Further, aspects, features, and/or advantages of the disclosed subjectmatter can be exploited in substantially any wireless telecommunicationor radio technology, e.g., IEEE 802.XX technology, e.g., Wi-Fi,Bluetooth, etc; WiMAX; enhanced GPRS; 3GPP LTE; 3GPP2; UMB; 3GPP UMTS;HSPA; high speed downlink packet access (HSDPA); high speed uplinkpacket access (HSUPA); LTE-A, GSM, NFC, Wibree, Zigbee, satellite, Wi-FiDirect, etc.

Further, selections of a radio technology, or radio access technology,can include second generation (2G), third generation (3G), fourthgeneration (4G), fifth generation (5G), x^(th) generation, etc.evolution of the radio access technology; however, such selections arenot intended as a limitation of the disclosed subject matter and relatedaspects thereof. Further, aspects, features, and/or advantages of thedisclosed subject matter can be exploited in disparate electromagneticfrequency bands. Moreover, one or more embodiments described herein canbe executed in one or more network elements, such as a mobile wirelessdevice, e.g., UE, and/or within one or more elements of a networkinfrastructure, e.g., radio network controller, wireless access point(AP), etc.

Moreover, terms like “user equipment,” (UE) “mobile station,” “mobilesubscriber station,” “access terminal,” “terminal”, “handset,”“appliance,” “machine,” “wireless communication device,” “cellularphone,” “personal digital assistant,” “smartphone,” “wireless device”,and similar terminology refer to a wireless device, or wirelesscommunication device, which is at least one of (1) utilized by asubscriber of a wireless service, or communication service, to receiveand/or convey data associated with voice, video, sound, and/orsubstantially any data-stream or signaling-stream; or (2) utilized by asubscriber of a voice over IP (VoIP) service that delivers voicecommunications over IP networks such as the Internet or otherpacket-switched networks. Further, the foregoing terms are utilizedinterchangeably in the subject specification and related drawings.

A communication network, e.g., corresponding to a network aware datadriven IoT communication environment (see e.g., 100, 200, etc.), forsystems, methods, and/or apparatus disclosed herein can include anysuitable mobile and/or wireline-based circuit-switched communicationnetwork including a GSM network, a time division multiple access (TDMA)network, a code division multiple access (CDMA) network, such as anInterim Standard 95 (IS-95) and subsequent iterations of CDMAtechnology, an integrated digital enhanced network (iDEN) network and aPSTN. Further, examples of the communication network can include anysuitable data packet-switched or combination datapacket/circuit-switched communication network, wired or wireless IPnetwork such as a VoLTE network, a VoIP network, an IP data network, aUMTS network, a GPRS network, or other communication networks thatprovide streaming data communication over IP and/or integrated voice anddata communication over combination data packet/circuit-switchedtechnologies.

Similarly, one of ordinary skill in the art will appreciate that awireless system e.g., a wireless communication device, UE 1002, etc. forsystems, methods, and/or apparatus disclosed herein can include a mobiledevice, a mobile phone, a 4G, a 5G, etc. cellular communication device,a PSTN phone, a cellular communication device, a cellular phone, asatellite communication device, a satellite phone, a VoIP phone, WiFiphone, a dual-mode cellular/WiFi phone, a combinationcellular/VoIP/WiFi/WiMAX phone, a portable computer, or any suitablecombination thereof. Specific examples of a wireless system can include,but are not limited to, a cellular device, such as a GSM, TDMA, CDMA,IS-95 and/or iDEN phone, a cellular/WiFi device, such as a dual-modeGSM, TDMA, IS-95 and/or iDEN/VoIP phones, UMTS phones, UMTS VoIP phones,or like devices or combinations thereof.

The disclosed subject matter can be implemented as a method, apparatus,or article of manufacture using standard programming and/or engineeringtechniques to produce software, firmware, hardware, or any combinationthereof to control a computer to implement the disclosed subject matter.The term “article of manufacture” as used herein is intended toencompass a computer program accessible from any computer-readabledevice, computer-readable carrier, or computer-readable media. Forexample, computer-readable media can include, but are not limited to,magnetic storage devices, e.g., hard disk; floppy disk; magneticstrip(s); optical disk (e.g., compact disk (CD), digital video disc(DVD), Blu-ray Disc (BD)); smart card(s); and flash memory device(s)(e.g., card, stick, key drive); and/or a virtual device that emulates astorage device and/or any of the above computer-readable media.

In accordance with various aspects of the subject specification,artificial intelligence based systems, components, etc. can employclassifier(s) that are explicitly trained, e.g., via a generic trainingdata, via policy rules of a policy framework, etc. as well as implicitlytrained, e.g., via observing characteristics of communication equipment,e.g., a gateway, a wireless communication device, etc., by receivingreports from such communication equipment, by receiving operatorpreferences, by receiving historical information, by receiving extrinsicinformation, etc.

For example, support vector machines can be configured via a learning ortraining phase within a classifier constructor and feature selectionmodule. Thus, the classifier(s) can be used by an artificialintelligence system to automatically learn and perform a number offunctions, e.g., performed by a wireless device (e.g., 110), includingbut not limited to: creating an RF fidelity layer within an upperportion of a protocol stack of the wireless device; monitoring, via theRF fidelity layer, a characteristic of an RF link between the wirelessdevice and an AP device; and in response to the characteristic of the RFlink being determined to satisfy a defined condition representing that afidelity of the RF link is lossy, preempting, via the RF fidelity layer,a transmission of data from the wireless device to a host device tofacilitate a reduction in transmission control protocol basedretransmissions of the data occurring under lossy condition(s) of the RFlink.

A classifier can be a function that maps an input attribute vector,x=(x1, x2, x3, x4, xn), to a confidence that the input belongs to aclass, that is, f(x)=confidence (class). Such classification can employa probabilistic and/or statistical-based analysis (e.g., factoring intothe analysis utilities and costs) to infer an action that a user desiresto be automatically performed. In the case of communication systems, forexample, attributes can be information received from access points,services, components of a wireless communication network, etc., and theclasses can be categories or areas of interest (e.g., levels ofpriorities). A support vector machine is an example of a classifier thatcan be employed. The support vector machine operates by finding ahypersurface in the space of possible inputs, which the hypersurfaceattempts to split the triggering criteria from the non-triggeringevents. Intuitively, this makes the classification correct for testingdata that is near, but not identical to training data. Other directedand undirected model classification approaches include, e.g., naïveBayes, Bayesian networks, decision trees, neural networks, fuzzy logicmodels, and probabilistic classification models providing differentpatterns of independence can be employed. Classification as used hereincan also be inclusive of statistical regression that is utilized todevelop models of priority.

As used herein, the term “infer” or “inference” refers generally to theprocess of reasoning about, or inferring states of, the system,environment, user, and/or intent from a set of observations as capturedvia events and/or data. Captured data and events can include user data,device data, environment data, data from sensors, sensor data,application data, implicit data, explicit data, etc. Inference can beemployed to identify a specific context or action, or can generate aprobability distribution over states of interest based on aconsideration of data and events, for example.

Inference can also refer to techniques employed for composinghigher-level events from a set of events and/or data. Such inferenceresults in the construction of new events or actions from a set ofobserved events and/or stored event data, whether the events arecorrelated in close temporal proximity, and whether the events and datacome from one or several event and data sources. Various classificationschemes and/or systems (e.g., support vector machines, neural networks,expert systems, Bayesian belief networks, fuzzy logic, and data fusionengines) can be employed in connection with performing automatic and/orinferred action in connection with the disclosed subject matter.

Further, the word “exemplary” and/or “demonstrative” is used herein tomean serving as an example, instance, or illustration. For the avoidanceof doubt, the subject matter disclosed herein is not limited by suchexamples. In addition, any aspect or design described herein as“exemplary” and/or “demonstrative” is not necessarily to be construed aspreferred or advantageous over other aspects or designs, nor is it meantto preclude equivalent exemplary structures and techniques known tothose of ordinary skill in the art having the benefit of the instantdisclosure.

Furthermore, to the extent that the terms “includes,” “has,” “contains,”and other similar words are used in either the detailed description orthe appended claims, such terms are intended to be inclusive—in a mannersimilar to the term “comprising” as an open transition word—withoutprecluding any additional or other elements. Moreover, the term “or” isintended to mean an inclusive “or” rather than an exclusive “or”. Thatis, unless specified otherwise, or clear from context, “X employs A orB” is intended to mean any of the natural inclusive permutations. Thatis, if X employs A; X employs B; or X employs both A and B, then “Xemploys A or B” is satisfied under any of the foregoing instances. Inaddition, the articles “a” and “an” as used in this application and theappended claims should generally be construed to mean “one or more”unless specified otherwise or clear from context to be directed to asingular form.

The above description of illustrated embodiments of the subjectdisclosure, including what is described in the Abstract, is not intendedto be exhaustive or to limit the disclosed embodiments to the preciseforms disclosed. While specific embodiments and examples are describedherein for illustrative purposes, various modifications are possiblethat are considered within the scope of such embodiments and examples,as those skilled in the relevant art can recognize.

In this regard, while the disclosed subject matter has been described inconnection with various embodiments and corresponding Figures, whereapplicable, it is to be understood that other similar embodiments can beused or modifications and additions can be made to the describedembodiments for performing the same, similar, alternative, or substitutefunction of the disclosed subject matter without deviating therefrom.Therefore, the disclosed subject matter should not be limited to anysingle embodiment described herein, but rather should be construed inbreadth and scope in accordance with the appended claims below.

What is claimed is:
 1. A method, comprising: determining, by a wirelessdevice comprising a processor, a characteristic of a radio frequencychannel wirelessly coupling the wireless device to an access pointdevice that has been configured to transfer data, which has beenreceived from the wireless device, to a host device; and in response tothe characteristic of the radio frequency channel being determined tosatisfy a defined condition representing a degradation of a fidelity ofthe radio frequency channel, modifying, by the wireless device based ona determined classification of outbound data of the data that has beendirected to the host device, a transmission of the outbound data tofacilitate a reduction in wireless retransmissions of the outbound datadue to the degradation of the fidelity of the radio frequency channel.2. The method of claim 1, wherein the determining of the characteristiccomprises: obtaining, via an attention command, the characteristic ofthe radio frequency channel from a transceiver device of the wirelessdevice.
 3. The method of claim 1, wherein the modifying of thetransmission of the outbound data comprises: in response to the outbounddata being determined to comprise a non-urgent type of communication,withholding the transmission of the non-urgent type of communication. 4.The method of claim 3, wherein the withholding of the transmission ofthe outbound data comprises: storing the non-urgent type ofcommunication in a first-in-first-out buffer as stored data tofacilitate a delayed transmission of the non-urgent type ofcommunication.
 5. The method of claim 4, wherein the defined conditioncomprises a first defined condition, and wherein the operations furthercomprise: in response to the characteristic of the radio frequencychannel being determined to satisfy a second defined conditionrepresenting the fidelity of the radio frequency channel has improved,sending the non-urgent type of communication directed to the hostdevice.
 6. The method of claim 3, wherein the modifying of thetransmission of the outbound data comprises: in response to the outbounddata being determined to comprise an urgent type of communication,sending the urgent type of communication directed to the host device. 7.The method of claim 1, wherein the wireless device has been configuredto send the outbound data directed to the host device using a datachannel wirelessly coupling the wireless device to the access pointdevice, wherein the radio frequency channel comprises a control channel,and wherein the determining of the characteristic comprises: determininga control channel characteristic of the control channel corresponding tocontrol based communications between the wireless device and the accesspoint device.
 8. A system, comprising: a processor; and a memory thatstores executable instructions that, when executed by the processor,facilitate performance of operations, comprising: determining acharacteristic of a radio frequency channel wireles sly coupling awireless device to an access point device that has been configured totransfer data between the wireless device and the system; and inresponse to the characteristic of the radio frequency channel beingdetermined to satisfy a defined condition representing a degradation ofa fidelity of the radio frequency channel, modifying, based on apriority level of an outgoing portion of the data, a transmission of theoutgoing portion from the system to the wireless device, thetransmission to facilitate a reduction of wireless retransmissions ofthe outgoing portion due to the degradation of the fidelity of the radiofrequency channel.
 9. The system of claim 8, wherein the data comprisesincoming data that has been received from the wireless device, andwherein the determining the characteristic comprises: determining thecharacteristic of the radio frequency channel based on a classificationof the incoming data.
 10. The system of claim 9, wherein the definedcondition comprises a first defined condition, wherein the outgoingportion of the data comprises a non-priority communication, and whereinthe modifying the transmission of the outgoing portion of the datacomprises: in response to the classification of the incoming data beingdetermined to satisfy a second defined condition with respect to anamount of priority communications that have been received during adefined period of time, delaying the transmission of the non-prioritycommunication.
 11. The system of claim 10, wherein the operationsfurther comprise: in response to the characteristic of the radiofrequency channel being determined to satisfy a third defined conditionrepresenting an improvement of the fidelity of the radio frequencychannel, sending the non-priority communication directed to the wirelessdevice.
 12. The system of claim 9, wherein the defined conditioncomprises a first defined condition, wherein the outgoing portion of thedata comprises a non-priority communication, and wherein the modifyingthe transmission of the outgoing portion of the data comprises: inresponse to the classification of the incoming data being determined tosatisfy a second defined condition with respect to an amount ofnon-priority communications that have been received during a definedperiod of time, sending the non-priority communication directed towireless device.
 13. The system of claim 9, wherein the definedcondition comprises a first defined condition, wherein the outgoingportion of the data comprises a priority communication, and wherein themodifying the transmission of the outgoing portion of the datacomprises: in response to the classification of the incoming data beingdetermined to satisfy a second defined condition with respect to anamount of priority communications that have been received during adefined period of time, sending the priority communication directed towireless device.
 14. The system of claim 8, wherein the data comprisesincoming data that has been received from the wireless device, andwherein the determining the characteristic comprises: determining thecharacteristic of the radio frequency channel based on appendedinformation representing the fidelity of the radio frequency channelthat has been appended to the incoming data.
 15. The system of claim 14,wherein a host application comprises the executable instructions, andwherein the operations further comprises: removing the appendedinformation from the incoming data to obtain application data; andforwarding the application data to the host application to facilitatefurther processing of the application data.
 16. The system of claim 14,wherein the outgoing portion of the data comprises a non-prioritycommunication, and wherein the modifying the transmission of theoutgoing portion of the data comprises: in response to determining,based on the appended information, that the characteristic of the radiofrequency channel satisfies the defined condition representing thedegradation of the fidelity of the radio frequency channel, delaying thetransmission of the non-priority communication.
 17. The system of claim14, wherein the outgoing portion of the data comprises a prioritycommunication, and wherein the modifying the transmission of theoutgoing portion of the data comprises: in response to determining,based on the appended information, that the characteristic of the radiofrequency channel satisfies the defined condition representing thedegradation of the fidelity of the radio frequency channel, sending thepriority communication directed to the wireless device.
 18. Amachine-readable storage medium, comprising executable instructionsthat, when executed by a processor, facilitate performance ofoperations, comprising: creating a radio frequency fidelity layer withinan upper portion of a protocol stack of a wireless device; monitoring,via the radio frequency fidelity layer, a characteristic of a radiofrequency link between the wireless device and an access point device;and in response to the characteristic of the radio frequency link beingdetermined to satisfy a defined condition representing that a fidelityof the radio frequency link is lossy, preempting, via the radiofrequency fidelity layer, a transmission of data from the wirelessdevice to a host device to facilitate a reduction in transmissioncontrol protocol based retransmissions of the data occurring under alossy condition of the radio frequency link.
 19. The machine-readablestorage medium of claim 18, wherein the monitoring of the characteristiccomprises: monitoring the characteristic of the radio frequency linkcorresponding to a control channel between the wireless device and theaccess point device.
 20. The machine-readable storage medium of claim18, wherein the data comprises a non-urgent communication, and whereinthe preempting the transmission comprises: delaying a transmission ofthe non-urgent communication.